home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Atari Mega Archive 1
/
Atari Mega Archive - Volume 1.iso
/
program
/
rcs5ap1b.lzh
/
CI.1LP
next >
Wrap
Text File
|
1991-01-30
|
12KB
|
331 lines
CI(1) Programmer's Manual CI(1)
NAME
ci - check in RCS revisions
SYNOPSIS
ci [_✓o_✓p_✓t_✓i_✓o_✓n_✓s] _✓f_✓i_✓l_✓e ...
DESCRIPTION
ci stores new revisions into RCS files. Each file name end-
ing in ,v is taken to be an RCS file. All others are
assumed to be working files containing new revisions. ci
deposits the contents of each working file into the
corresponding RCS file. If only a working file is given, ci
tries to find the corresponding RCS file in an RCS subdirec-
tory and then in the working file's directory. For more
details, see FILE NAMING below.
For ci to work, the caller's login must be on the access
list, except if the access list is empty or the caller is
the superuser or the owner of the file. To append a new
revision to an existing branch, the tip revision on that
branch must be locked by the caller. Otherwise, only a new
branch can be created. This restriction is not enforced for
the owner of the file if non-strict locking is used (see
rcs(1)). A lock held by someone else may be broken with the
rcs command.
Normally, ci checks whether the revision to be deposited is
different from the preceding one. If it is not different,
ci aborts the deposit, asking beforehand if possible. A
deposit can be forced with the -f option.
For each revision deposited, ci prompts for a log message.
The log message should summarize the change and must be ter-
minated by end-of-file or by a line containing . by itself.
If several files are checked in ci asks whether to reuse the
previous log message. If the standard input is not a termi-
nal, ci suppresses the prompt and uses the same log message
for all files. See also -m.
The number of the deposited revision can be given by any of
the options -f, -I, -k, -l, -q, -r, or -u.
If the RCS file does not exist, ci creates it and deposits
the contents of the working file as the initial revision
(default number: 1.1). The access list is initialized to
empty. Instead of the log message, ci requests descriptive
text (see -t below).
OPTIONS
-r[_✓r_✓e_✓v]
assigns the revision number _✓r_✓e_✓v to the checked-in revi-
sion, releases the corresponding lock, and deletes the
Printed 1/29/91 1990/12/04 1
CI(1) Programmer's Manual CI(1)
working file. This is the default. _✓r_✓e_✓v may be sym-
bolic, numeric, or mixed.
If _✓r_✓e_✓v is a revision number, it must be higher than the
latest one on the branch to which _✓r_✓e_✓v belongs, or must
start a new branch.
If _✓r_✓e_✓v is a branch rather than a revision number, the
new revision is appended to that branch. The level
number is obtained by incrementing the tip revision
number of that branch. If _✓r_✓e_✓v indicates a non-existing
branch, that branch is created with the initial revi-
sion numbered _✓r_✓e_✓v.1.
If _✓r_✓e_✓v is omitted, ci tries to derive the new revision
number from the caller's last lock. If the caller has
locked the tip revision of a branch, the new revision
is appended to that branch. The new revision number is
obtained by incrementing the tip revision number. If
the caller locked a non-tip revision, a new branch is
started at that revision by incrementing the highest
branch number at that revision. The default initial
branch and level numbers are 1.
If _✓r_✓e_✓v is omitted and the caller has no lock, but owns
the file and locking is not set to _✓s_✓t_✓r_✓i_✓c_✓t, then the
revision is appended to the default branch (normally
the trunk; see the -b option of rcs(1)).
Exception: On the trunk, revisions can be appended to
the end, but not inserted.
-f[_✓r_✓e_✓v]
forces a deposit; the new revision is deposited even it
is not different from the preceding one.
-k[_✓r_✓e_✓v]
searches the working file for keyword values to deter-
mine its revision number, creation date, state, and
author (see co(1)), and assigns these values to the
deposited revision, rather than computing them locally.
It also generates a default login message noting the
login of the caller and the actual checkin date. This
option is useful for software distribution. A revision
that is sent to several sites should be checked in with
the -k option at these sites to preserve the original
number, date, author, and state. The extracted keyword
values and the default log message may be overridden
with the options -d, -m, -s, -w, and any option that
carries a revision number.
-l[_✓r_✓e_✓v]
Printed 1/29/91 1990/12/04 2
CI(1) Programmer's Manual CI(1)
works like -r, except it performs an additional co -l
for the deposited revision. Thus, the deposited revi-
sion is immediately checked out again and locked. This
is useful for saving a revision although one wants to
continue editing it after the checkin.
-u[_✓r_✓e_✓v]
works like -l, except that the deposited revision is
not locked. This lets one read the working file
immediately after checkin.
-q[_✓r_✓e_✓v]
quiet mode; diagnostic output is not printed. A revi-
sion that is not different from the preceding one is
not deposited, unless -f is given.
-I[_✓r_✓e_✓v]
interactive mode; the user is prompted and questioned
even if the standard input is not a terminal.
-d[_✓d_✓a_✓t_✓e]
uses _✓d_✓a_✓t_✓e for the checkin date and time. The _✓d_✓a_✓t_✓e is
specified in free format as explained in co(1). This
is useful for lying about the checkin date, and for -k
if no date is available. If _✓d_✓a_✓t_✓e is empty, the working
file's time of last modification is used.
-m_✓m_✓s_✓g
uses the string _✓m_✓s_✓g as the log message for all revi-
sions checked in.
-n_✓n_✓a_✓m_✓e
assigns the symbolic name _✓n_✓a_✓m_✓e to the number of the
checked-in revision. ci prints an error message if
_✓n_✓a_✓m_✓e is already assigned to another number.
-N_✓n_✓a_✓m_✓e
same as -n, except that it overrides a previous assign-
ment of _✓n_✓a_✓m_✓e.
-s_✓s_✓t_✓a_✓t_✓e
sets the state of the checked-in revision to the iden-
tifier _✓s_✓t_✓a_✓t_✓e. The default state is Exp.
-t_✓f_✓i_✓l_✓e
writes descriptive text from the contents of the named
_✓f_✓i_✓l_✓e into the RCS file, deleting the existing text.
The _✓f_✓i_✓l_✓e name may not begin with -.
-t-_✓s_✓t_✓r_✓i_✓n_✓g
Write descriptive text from the _✓s_✓t_✓r_✓i_✓n_✓g into the RCS
file, deleting the existing text.
Printed 1/29/91 1990/12/04 3
CI(1) Programmer's Manual CI(1)
The -t option, in both its forms, has effect only dur-
ing an initial checkin; it is silently ignored other-
wise.
During the initial checkin, if -t is not given, ci
obtains the text from standard input, terminated by
end-of-file or by a line containing . by itself. The
user is prompted for the text if interaction is possi-
ble; see -I.
For backward